I am getting these below errors on my windows 2008 R2 server. Can somebody tell what this is about ? Event ID 6281 System Integrity Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error. File Name: \Device\HarddiskVolume2\Windows\System32\l3codeca.acm

Hello Shahid, Is this a Terminal Server or are we using RDP? Do we have audio redirection enabled?Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. Volume Activation documentation on TechNet http://technet.microsoft.com/en-us/windows/dd197314.aspx http://technet.microsoft.com/en-us/library/dd996588.aspx VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

yes most of these machines are also hosting TS role. Yes we are managing these through RDP. Audio redirection is what is there by default. Do you mean to say this error is related to Audio redirection of RDP ? can you shed more light, we just want to know the severity of this error actually we are having another serious problem of strange system behavior for one of the machines and suspect is on this

Hello Shahid Roofi, Yes, when audio is redirected to the client and we load audiodg, it enumerates the codecs to get information from them. Not all codecs are signed to load in a protected process and if they are not this error is generated. more on the protected process http://www.microsoft.com/whdc/driver/install/drvsign/pmp-sign.mspx you should be able to ignore the error.Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. Volume Activation documentation on TechNet http://technet.microsoft.com/en-us/windows/dd197314.aspx http://technet.microsoft.com/en-us/library/dd996588.aspx VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Since Darrell's explanation implies that the codec will not be loaded, we can assume it's safe to disable the problematic codec to avoid logging the error in the future. http://kb2.adobe.com/cps/408/kb408929.html covers how to disable codecs: Identify problematic windows codecs To identify problematic Windows codecs, disable one codec at a time and try to re-create the problem after you disable each one. Don't disable codecs that were included with Windows 7 or Vista. See Video and Audio Codecs Included with Windows 7 and Vista below for a list of such codecs. Disclaimer: This task requires you to modify the Windows registry. The registry contains system-related information that is critical to your computer and applications. Before modifying the registry, always make a backup copy of it. Adobe doesn't provide support for problems that arise from improperly modifying the registry. For information about the Windows registry or the Registry Editor, see the documentation in Windows or contact Microsoft Technical Support or your computer's manufacturer. Close all applications.Choose Start, type regedit in the Search textbox, and press Enter.In the left pane of the Registry Editor, navigate to the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Drivers32Select Drivers32.Choose File > Export.In the Export Registry File dialog box, select Selected Branch under Export Range, enter a name and location for the backup registry key, and then click Save.In the right pane of the Registry Editor, double-click the name of a codec. (For example, double-clickvidc.msvc.)In the Edit String dialog box, enter a colon (:) at the beginning of the Value Data, and then click OK. (For example, the value data would now be :msvidc32.dll.)Start the Adobe application and try to re-create the problem.Do one of the following: If the problem does not recur, then the codec that you disabled in Step 8 is the cause. Close the Adobe application and the Registry Editor. Leave this codec disabled and then contact its developer for additional support.If the problem recurs, then the codec you disabled in Step 8 is not the cause. Close the Adobe application and then repeat Steps 7 through 9 for a different codec. Once you have identified the problematic codec or codecs, re-enable any other codecs that you disabled. If the problem recurs after you have disabled all of the codecs listed in Drivers32, then Windows codecs are not the cause. You can reenable them. To re-enable Windows codecs: In the right pane of the Registry Editor, double-click the name of a disabled codec. (For example, double-click vidc.msvc.)In the Edit String dialog box, remove the colon (:) from the beginning of the Value Data, and then click OK. (For example, the value data would now be msvidc32.dll.)Repeat Steps 1 and 2 for any other codec that you disabled. (Do not re-enable any codecs that you determined were causing the problem in Step 10 above.)Close the Registry Editor. <small> My unanswered threads: DFS / RDC size estimations? Online backup of Active Directory / ESE DB, command line interface to ESENT.DLL's JetBackup() function. </small>